First time confirmation of database entry

ABSTRACT

Provided is an apparatus that stores a formulary. The apparatus includes a memory device that stores the formulary, the formulary comprising a plurality of drug entries. A user input device allows a user to verify a drug of the plurality of drug entries of the formulary. A code reader interprets computer-readable codes. After a computer-readable code that is associated with the drug is read by the code reader, the drug is verified using the user input device.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This application relates to drug databases used in medical facilities,and to devices and methods employing such databases.

2. Description of Related Art

Medical facilities, such as hospitals, can have a pharmacy that storesdrugs used within the facility. The drugs are dispensed under thesupervision of a pharmacist. For example, the pharmacist might dispensedrugs from the pharmacy to an anesthesiologist for use during a surgicalprocedure.

Information about various drugs including, but not limited to, the drugsstored in the pharmacy, can be saved in a database (e.g., a master drugdatabase “MDD”). The MDD is accessible to authorized users in themedical facility, such as the pharmacist. To facilitate inventorying andtracking of drugs within the medical facility, the drugs can beidentified by computer-readable codes, as provided by barcodes,radio-frequency identification (RFID) tags, or other types of codescapable of being read in a non-contact manner. The database can storeinformation about a particular drug, such as a drug name, concentration,expiration date, etc., in association with a particularcomputer-readable code for the drug. Such information can be retrievedfrom the database when the code is read by a device capable ofinterpreting such codes (i.e., “a code reader”). Example code readersinclude barcode scanners, RFID readers and the like.

Since a computer-readable code is not easily interpreted by a person,labeling errors can go undetected. For example, a barcode associatedwith a first type of drug could unknowingly be placed on a second typeof drug. When the barcode is subsequently scanned, information about thefirst type of drug will be retrieved from the database. This could leada person to who is actually administering or dispensing the second typeof drug to erroneously believe that they are administering or dispensingthe first type of drug. Similarly, errors in the database itself couldlead to a barcode for the first type of drug being placed onto a secondtype of drug.

BRIEF SUMMARY OF THE INVENTION

Accordingly, it would be desirable to verify the drug in the databaseand/or verify information about the drug.

According to one aspect, provided is an apparatus that stores aformulary. The apparatus includes a memory device that stores theformulary, the formulary comprising a plurality of drug entries. A userinput device allows a user to verify a drug of the plurality of drugentries of the formulary. A code reader interprets computer-readablecodes. After a computer-readable code that is associated with the drugis read by the code reader, the drug is verified using the user inputdevice.

According to another aspect, provided is a method of confirming druginformation. A plurality of drug entries, each associated with acomputer-readable code, are received. The plurality of drug entries arestored on a memory device. A code reader reads the computer-readablecode associated with a drug of the plurality of drug entries. A user isautomatically prompted to verify the drug after reading, by the codereader, the computer-readable code associated with the drug. An input isreceived from the user verifying the drug.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention may take physical form in certain parts and arrangement ofparts, embodiments of which will be described in detail in thisspecification and illustrated in the accompanying drawings which form apart hereof and wherein:

FIG. 1 is a schematic diagram of a portion of a medical computer networkfor generating a label to be applied to a container storing a medicinalsubstance;

FIG. 2 is a perspective view of an example computer terminal of themedical computer network;

FIG. 3 shows a block diagram of the example computer terminal;

FIG. 4 shows an example medical label;

FIG. 5 is a perspective view of a syringe provided with a medical label;and

FIG. 6 is a flow diagram.

DETAILED DESCRIPTION OF THE INVENTION

Certain terminology is used herein for convenience only and is not to betaken as a limitation on the present invention. Relative language usedherein is best understood with reference to the drawings, in which likenumerals are used to identify like or similar items. Further, in thedrawings, certain features may be shown in somewhat schematic form.

It is also to be noted that the phrase “at least one of”, if usedherein, followed by a plurality of members herein means one of themembers, or a combination of more than one of the members. For example,the phrase “at least one of a first widget and a second widget” means inthe present application: the first widget, the second widget, or thefirst widget and the second widget. Likewise, “at least one of a firstwidget, a second widget and a third widget” means in the presentapplication: the first widget, the second widget, the third widget, thefirst widget and the second widget, the first widget and the thirdwidget, the second widget and the third widget, or the first widget andthe second widget and the third widget.

FIG. 1 shows a portion of a medical labeling network 5. The networkincludes a plurality of operating room (“OR”) computer terminals 10 a,10 b, 10 c (referred to generally at 10), a database server 11, and apharmacy computer terminal 13. The computer terminal 10 is referred toas an OR computer terminal out of convenience, to explain the drawingsin the context of a medical facility (e.g., a hospital). The OR computerterminal 10 can, but need not be, located in an operating room orotherwise associated with an operating room where a surgical procedurecan be performed on a patient.

A master drug database (“MDD”) is stored on the database server 11.Alternatively, the MDD can be stored on the pharmacy computer terminal13. The MDD can contain an identity, identification code (e.g., NDC)number, concentration, any other pertinent information for drugs used inthe hospital, or any combination thereof. The pharmacy computer terminal13 can execute computer-executable instructions embodied as a softwareprogram stored in a computer memory provided to the pharmacy computerterminal 13 called an administration tool (“AT”). The AT can be used bya pharmacist to create and distributed a formulary including a subset ofthe entries found in the MDD to the OR computer terminals 10. The AT canalso optionally be used to retrieve drug information from the MDD,update the MDD (e.g., add new drugs to the database or modify existingdrug information), etc.

Based on information contained in the MDD, the pharmacist creates andmanages a formulary 54 to be stored in a memory device 24 (see FIG. 3)of one or more of the OR computer terminals 10, as described in detailin U.S. patent application Ser. No. 13/274,184, which is herebyincorporated in its entirety by reference herein. The formulary caninclude a subset of the MDD selected and added to the formulary 54 usingthe AT, and the subset can optionally comprise those drugs that arecommonly used in the operating room or other location at the medicalfacility where the OR computer terminal 10 is positioned. The sameformulary can optionally be stored in the memory device 24 of more thanone computer terminal, and can optionally be customized to include drugsutilized during surgical procedures relating to a particular medicaldiscipline. For example, the same formulary comprising drugs commonlyused during cardiac surgical procedures may be stored in the memorydevice 24 of multiple computer terminals, which are each located in arespective operating room dedicated for such procedures. Another,different formulary comprising drugs, optionally in appropriate doses,suitable to be administered to children can be stored in the memory of acomputer terminal located in an operating room dedicated for pediatricsurgical procedures. According to alternate embodiments, the formulary54 stored in the memory device 24 of the OR computer terminal 10 can beevaluated and updated, replaced or otherwise changed before eachsurgical procedure if the operating room where the OR computer terminal10 is located is not dedicated for a particular type of surgicalprocedure.

When a formulary update is needed to accommodate a specific type ofprocedure, a pharmacist or other authorized individual can create a newor updated formulary with the AT. The new or updated formulary, oncecomplete, can be transmitted over the network 5 (e.g., LAN, WAN or both)in FIG. 1 to each of the OR computer terminals 10 that are to replacethe existing formulary in the memory device 24 in of the OR computerterminal 10 with the new or updated formulary. The new or updatedformulary can be transmitted from the pharmacy computer terminal 13 tothe OR computer terminal 10 via the network 5 or, according to alternateembodiments, can be transferred to the OR computer terminal 10 from aportable memory device, such as a USB flash memory for example. Oncetransmitted to the OR computer terminal 10, the formulary is availableto be used by the OR computer terminal 10 to relate computer-readablecodes scanned as described below to a drug in the formulary. Thus, theOR computer terminal 10 can identify drugs based on suchcomputer-readable codes without operator intervention.

One or both of the OR computer terminal 10 and the administration toolAT on the pharmacy computer terminal 13 provide the user (e.g.,pharmacist, doctor, etc.) with an opportunity to verify a drug in theformulary. The verification can occur before the drug is entered intothe formulary or after the drug is entered into the formulary using theAT on the pharmacy computer terminal 13, and can occur before theformulary is created, while the formulary is being created, or after theformulary is created. Drug verification can also optionally be performedusing the AT before the formulary is transmitted to the OR computerterminal 10, using the OR computer terminal that has already receivedthe formulary, or a combination thereof. Regardless of whereverification is received from a user, e.g., with the OR computerterminal 10, with the AT running on the pharmacy computer terminal 13,or elsewhere in a network, once a drug included in a formulary has beenverified as being correctly identified by a computer readable code, thefact that verification has occurred for that drug can be indicated inthe formulary so the next time that drug is subsequently identified by acomputer readable code verification can be omitted (i.e., not requiredsubsequent to first time verification).

Verifying the drug involves receiving, with the OR computer terminal 10,the pharmacy computer terminal 13, or other computer terminal,manually-input confirmation from a user that drug information returnedin response to scanning a computer-readable code does indeed correspondto the drug associated with that computer-readable code. For example, alabel applied to a drug vial storing propofol may include a barcode thatis to be scanned by a code reader 18 such as a barcode scanner providedto the OR computer terminal 10 or pharmacy computer 13. In response toscanning that barcode, the OR computer terminal 10 or pharmacy computer13 interprets the barcode to determine an identification number andretrieves an entry from the formulary assigned to that identificationnumber. The relevant information of that entry can be displayed by adisplay connected to the OR or pharmacy computer terminal, audiblybroadcast via a speaker, or a combination thereof. The user can comparethe returned drug information with drug information printed on the labelon the drug vial to make sure that they match. The drug informationstored in the MDD or formulary can be displayed on a display device atthe pharmacy computer terminal 13 or the OR computer terminal 10, oraudibly broadcast by a speaker at such computer terminals, or printed bya printer 26 at such computer terminals. The display device and speakerare example interface devices for conveying drug information to a user.The user can confirm that drug information printed on the drug'scontainer or packaging matches the information in the MDD or formularythrough an input device (e.g., push button, soft key, etc.) at thepharmacy computer terminal 13 or the OR computer terminal 10. Theinterface device and the input device can optionally be integrated in acommon user interface.

In certain embodiments, the pharmacy computer terminal 13 and the ORcomputer terminal 10 include code readers (e.g., barcode readers, RFIDreaders, etc.) that read computer-readable codes associated with thedrugs in the MDD and formulary. As an example, FIG. 4 illustrates alabel that can be applied to a drug vial or other drug packagingincluding a barcode 50, which in the present example is a Data Matrixtwo-dimensional barcode. When the barcode 50 is scanned by the codereader, the pharmacy computer terminal 13 or OR computer terminal 10that communicates with the code reader can retrieve and display druginformation associated with the barcode. The user can then manuallyinput verification that the retrieved drug information matches theinformation printed on the drug's container or packaging.

The interface device at the pharmacy computer terminal 13 and/or the ORcomputer terminal can prompt the user to verify that a drug entry in theformulary matches the drug information printed on the drug's containeror packaging. For example, a display device such as a computer monitor,for example, can display an instruction to verify the retrieved druginformation, or the speaker can broadcast such an instruction. Theprompt can optionally be limited to occurring a single time, such as thefirst time the drug information is retrieved from the formulary inresponse to scanning a barcode, or optionally multiple times, such aseach time drug information is retrieved from the formulary in responseto scanning a barcode. In certain embodiments, an interface device iscontrolled to automatically generate the prompt seeking manualverification from the user after the drug's computer readable code isfirst read by the code reader. The OR computer terminal 10 and/orpharmacy computer 13 can optionally not prompt the user for verificationonce the drug information in that formulary has been verified at leastonce by an authorized user. That is, the drug's computer readable codecan be subsequently read again by the code reader after verification hasbeen received and associated with the verified drug entry in theformulary without the prompt being generated again.

Once the user verifies the drug, successful verification can be storedin the formulary for that particular drug entry in the memory 24 of theOR computer terminal 10 where verification was performed. According toalternate embodiments, successful verification can optionally betransmitted via the network 5 to be stored in association with that drugentry in the formulary stored by the memory of each OR computer terminal10 in a network such as a private LAN of a given medical facility, forexample. Thus, each formulary stored by an OR computer terminal 10having that particular drug entry can receive and store confirmation ofsuccessful verification to avoid requiring a user of those recipient ORcomputer terminals 10 from being prompted for verification the firsttime the drug entry is returned in response to scanning amachine-readable code associated with that drug. According to anotherembodiment, notice that verification of a drug entry has occurred at theOR computer terminal 10 can optionally be transmitted via email, textmessage, or other network communication to the pharmacy computerterminal 13; a handheld portable communication device 17 (FIG. 1) (e.g.,mobile phone, personal digital assistant (“PDA”), etc. . . . )designated for use by a person authorized to access and edit theformulary such as a pharmacist, for example. By transmittingnotification that verification has been received by one or more of theOR computer terminals 10, the pharmacist can ensure verification of thatparticular drug entry is included in the formulary 54 before theformulary 54 is distributed to the OR computer terminal(s) 10 in thefuture as part of a new formulary that is to entirely replace anexisting formulary.

As mentioned above, manual verification of drug entries in a formulary54 can optionally occur before the formulary 54 is delivered to the ORcomputer terminals 10. According to those embodiments, the pharmacistcan use a barcode scanner or other input device to read barcodes orother machine-readable codes associated with each drug entry in theformulary 54 to be verified. Those drug entries that are verified caninclude a record to that effect in the formulary, and the first timeverification of those drug entries can be omitted once the formulary 54is delivered to the OR computer terminals 10. In this manner, the usersof the OR computer terminals 10 may optionally not be prompted formanual verification the first time a barcode or other machine-readablecode is scanned for the verified drug entries.

Embodiments of the OR computer terminal 10 can optionally allow forbypassing first time verification. According to such embodiments, the ORcomputer terminal 10 can prompt the user to input verification via thetouch screen display 14 or other input device provided to the ORcomputer terminal 10. The options presented, however, can also include abypass command that, if selected, allows printing of a label asdescribed below to proceed without verification. A user who elects tobypass verification and trust the drug information returned in responseto scanning a barcode on a drug vial can continue with the process ofprinting a label. However, a record is created by the OR computerterminal 10 indicating that verification was bypassed. The user of theOR computer terminal can also optionally be required to be logged intothe OR computer terminal 10, so the identification of the authorizeduser who elects to bypass verification can also be included in therecord documenting the selection of the bypass option. Other informationsuch as the drug entry in the formulary, concentration, date, patientwho received the drug for which verification was bypassed, etc. . . .can also optionally be included in the bypass record.

In addition to receiving user verification of a drug, the OR computerterminal 10 is capable of generating a label identifying the drug, frominformation in the formulary. In particular, the label printed can berequired to conform to a labeling standard observed in the medical fieldgoverning the labeling of that drug. As shown in FIG. 2, the OR computerterminal 10 includes a touch-screen display 14 that displays a virtuallabel 16 to be printed as the label 12, and displays soft keys that canbe touched by a user to input data and commands into the OR computerterminal 10, such as the verification command discussed above. Thevirtual label 16 is a computer-generated rendering of the label 12 thatoffers the user visual confirmation of the appearance of the physicallabel 12 to be printed by a printer 26, and when verification isrequired, the virtual label 16 can optionally be compared to the labelbearing the barcode scanned to generate the virtual label 16 forverification purposes. A code reader 18 can be provided at a convenientlocation such as adjacent a bottom portion of the display 14 to read acomputer-readable code.

The OR computer terminal 10 includes a cabinet 20 housing componentsthat are operable to produce the label 12 in compliance with a medicallabeling standard. The cabinet 20 can also support the display 14 andthe code reader 18 to form a self-contained, stand-alone and monolithicunit. However, alternate embodiments include at least one of the display14, the code reader 18 and a printer 26 provided separately from thecabinet 20, to be positionable relative to the cabinet 20 as aperipheral that is operatively connected to the other componentssupported by the cabinet 20. The internal components housed within thecabinet 20 are schematically illustrated by the block diagram of FIG. 3.A computer processor 22 is provided to execute computer-executableinstructions stored in a non-transitory computer readable memory 24 suchas a hard disk drive, read-only memory (“ROM”), random access memory(“RAM”), optical disc, or any other suitable memory device. Theformulary 54 is also stored in the memory 24. A bus system 28facilitates communication between components such as the display 14,code reader 18, processor 22, memory 24 and printer 26.

The printer 26 includes a print head 30 for applying label content ontolabel stock delivered from a supply 32 of labels, which can be blank, orat least in partial compliance with a medical labeling standard. Theprint head 30 can fall within any category of printing technologysuitable to apply label content onto label stock. For example, the printhead 30 can be an inkjet print head that deposits droplets of ink in apattern to create the label content, a laser print head that directs alaser across a photoreceptor to create the pattern for the label contentto be printed, a solid-ink print head, a dot matrix print head, and thelike.

The label supply 32 can include a roll of label stock that has blanklabels supported on a release tape, a tray of individual blank labels,or any other source of labels on which label content is to be printed.The label supply 32 can be internally disposed within the printer 26 orfed into the printer from an external location.

FIG. 4 shows an illustrative embodiment of a label 12 to be generated bythe OR computer terminal 10. The label 12, as shown, includes labelcontent that is compliant with, and renders the label 12 compliant witha medical substance labeling standard. For example, the medicinalsubstance labeling standard can be the guidelines promulgated by theNational Safety Patient Goals of the Joint Commission, the AmericanSociety of Anesthesiologists, any other medicinal labeling standardestablished by a professional governing or trade organization or agovernmental organization, or any combination thereof. Such guidelinescan be based on other medicinal substance labeling standards such asthose created by ASTM International, for example. The medicinalsubstance labeling standards can also require specific sizes, colors andpatterns, type faces and other label content used on labels applied tounlabeled syringes that are filled by the users (i.e., those who willadminister the medicinal substance to the patient) or their agents toidentify the medicinal substance. Such standards are typically notintended to govern the requirements of labels applied by the drugmanufacturer.

The label content required to render the label 12 compliant with alabeling standard created to govern the labeling of any material in themedical field can be specific to the particular standard against whichcompliance is to be measured. For instance, depending on the medicinalsubstance labeling standard, the label content can include one, aplurality, or all of the following:

a concentration of a drug to be identified by the label 12,

a dilution of a drug and a diluent used to dilute the drug;

a date and/or time at which the drug was prepared;

an expiration date and/or time of the drug to be labeled;

an identification of an individual who prepared the drug;

a warning about a risk associated with the drug; and

a color to be applied to the label 12 as required by the medicinalsubstance labeling standard for the particular drug to be labeled.

The illustrative embodiment of the label 12 in FIG. 4 is compliant witha medicinal substance labeling standard requiring the name 38 of thedrug, which is Propofol in the present embodiment, along with aconcentration 40 of the drug, which is 10 mg/mL. The name of the drugcan be printed using so-called “tall man lettering” to help emphasizethe difference between different medicinal substances with similarspellings. Tall man lettering requires printing a distinguishing portionof the name in all caps, and the remainder of the name in common withthe distinguished medicinal substance in lower case letters. The labelcontent 36 on the label 12 also includes the identity 42 of the personwho prepared the label 12 and/or the syringe of the medicinal substance,along with the date and time 44 the syringe of the medicinal substancewas prepared, and the expiration date and time 46 of that syringe of themedicinal substance.

The label 12 also includes a color code that is visible when viewing thecontent surface 34 of the label 12. For the illustrative embodiment inFIG. 4, the color code appears as a solid colored background 48 toprinted text such as the name 38, concentration 40, identity 42 of thepreparer, and preparation and expiration dates and times 44, 46. Thecolor code is specified in this example by the medicinal substancelabeling standard. For example, induction agents such as thiopental andketamine are identified by a solid yellow color code. Tranquilizers suchas diazepam and midazolam are identified by a solid orange colorbackground. Narcotics such as morphine and fentanyl are identified by asolid blue color background. Antagonist medicinal substances are denotedby diagonal stripes of the agonist color alternating with white stripes.

The color code can optionally be printed onto the content surface 34 aslabel content 36 by the printer 26. According to alternate embodiments,the color code is pre-applied to the label 12 to be visible when viewingthe content surface 34 by a manufacturer of the label stock before thelabel 12 is introduced to the printer 26. For such alternateembodiments, the appropriate pre-color-coded label stock is selectedfrom among available label stock that is pre-color coded with aplurality of different colors. Each of the different colors correspondsto a different medicinal substance in accordance with the medicinalsubstance labeling standard. Thus, several rolls of different coloredlabel stock may be available, and the appropriate roll having the colorcode corresponding to the medicinal substance to be labeled can beselected.

A computer-readable code 50 can also be printed by the printer 26 aslabel content 36 on the label 12. The computer-readable code can be abarcode, RFID code, or other suitable code that is indicative of themedicinal substance being labeled. For instance, the computer-readablecode 50 can represent the other label content 36, and optionally thecolor code, for integrating the labeling of the syringe or othercontainer with an Anesthesiology Information Management System (“AIMS”)or other hospital information system.

FIG. 5 shows an illustrative embodiment of a syringe 52 storing a drugthat is labeled with a label 12 as printed by the OR computer terminal10. As shown, the label 12 bearing the computer-readable code 50 can beapplied to the syringe 52 and, before administration of the drug, thecomputer-readable code 50 can be scanned by code reader 18 (FIG. 2)provided to the OR computer terminal 10. The OR computer terminal 10 canoptionally display the virtual label 16, and optionally audibly announcethe drug identified by the label 12 for confirmation purposes. The usercan verify the accuracy of the virtual label 16 by pressing a soft keyon the display 14 before the label is printed by the printer 26.

An example method of confirming drug information is shown in flowdiagram form in FIG. 6. In step 60, a plurality of drug entriesassociated computer-readable codes are received (e.g., received by theOR computer terminal, database server, and/or the pharmacy computerterminal). The plurality of drug entries are stored on a memory device(step 62), such as memory device 24 in the OR computer terminal (FIG.3), a memory device of the database server, and/or a memory device ofthe pharmacy computer terminal. A formulary including the plurality ofdrug entries is created from the MDD and received by the OR computerterminal (step 64). A code reader reads a computer-readable codeassociated with a drug included among the plurality of drug entries(step 66). In response to reading the computer-readable code, the ORcomputer terminal determines (step 68) whether the drug associated withthe computer-readable code has been verified (before the formulary wasreceived, by manual verification transmitted from another OR computerterminal 10, at the OR computer terminal itself, etc. . . . ). If not,the OR computer terminal 10 automatically prompts the user to verify thedrug after the computer-readable code is read by the code reader (step70). It is then determined (step 72) by the OR computer terminal 10whether the user has elected to bypass entering manual verification ofthe unverified drug information. If so, a record is established (step74) indicating that verification has been bypassed, and any otherpertinent information such as the identification of the user whobypassed verification. Input from a user is received, verifying the drug(step 70). If not, manual verification is received (step 76) and theprocess of printing a label proceeds (step 78). A notification that thedrug has been verified can also optionally be transmitted in response toreceiving verification at step 76 to a remote, network-connectedresource.

If, at step 68, it is determined that the retrieved drug information hasbeen verified, then label printing (step 78) proceeds without promptingthe user for verification.

Illustrative embodiments have been described, hereinabove. It will beapparent to those skilled in the art that the above devices and methodsmay incorporate changes and modifications without departing from thegeneral scope of this invention. It is intended to include all suchmodifications and alterations within the scope of the present invention.Furthermore, to the extent that the term “includes” is used in eitherthe detailed description or the claims, such term is intended to beinclusive in a manner similar to the term “comprising” as “comprising”is interpreted when employed as a transitional word in a claim.

What is claimed is:
 1. An apparatus that stores a formulary, theapparatus comprising: a memory device that stores the formulary, theformulary comprising a plurality of drug entries; a code reader thatreads a computer-readable code associated with a drug container andtransmits a signal indicative of data encoded by the computer-readablecode; a processor adapted to identify, based on the data encoded by thecomputer-readable code, a first drug entry included in the formularycorresponding to the data encoded by the computer-readable code; apresentation device that presents a user with an identity of a drugassociated with the first drug entry; and a user input device thatreceives input from the user indicating that the identity of the drugassociated with the first drug entry identified from among the pluralityof drug entries of the formulary based on the data encoded by thecomputer-readable code is consistent with information included on alabel associated with the drug container; wherein, after receiving theinput from the user, the processor stores an indication that theidentity of the drug has been verified in the formulary.
 2. Theapparatus of claim 1, wherein the identity of the drug is verifiedbefore being entered into the formulary.
 3. The apparatus of claim 1,wherein the identity of the drug is verified subsequent to the drugbeing entered into the formulary.
 4. The apparatus of claim 3, whereinafter verification of the drug entry in the formulary by the user, theinterface device omits further prompting of the user to verify the drugentry in the formulary.
 5. The apparatus of claim 1, further comprisingan interface device that prompts the user to verify the drug after thecomputer-readable code that is associated with the drug is read by thecode reader.
 6. The apparatus of claim 5, wherein the interface deviceautomatically prompts the user to verify a drug entry in the formularybased on a first read of the computer-readable code by the code readersubsequent to the drug entry being entered into the formulary.
 7. Theapparatus of claim 6, wherein after verification of the drug entry inthe formulary by the user, the interface device omits further promptingof the user to verify the drug entry in the formulary upon further readsof the computer-readable code by the code reader.
 8. The apparatus ofclaim 6, wherein after verification of the drug entry in the formularyby the user, the apparatus transmits a notification of the verificationto a remote apparatus over a communication network.
 9. The apparatus ofclaim 1, wherein the code reader comprises a barcode scanner, and thecomputer-readable code comprises a barcode, the apparatus furthercomprising a printer for printing a label, wherein the label iscompliant with a medical labeling standard.
 10. The apparatus of claim 1further comprising a network adaptor that transmits a notificationindicating that verification of the drug has occurred using the userinput device provided to the apparatus storing the formulary over acommunication network addressed to a recipient with authorization toaccess and edit the formulary.
 11. A method of confirming druginformation, comprising the steps of: receiving a plurality of drugentries that collectively form a formulary, each of said drug entriesbeing associated with a different computer-readable code; storing theplurality of drug entries on a non-transitory computer memory device;reading, with a code reader, a first computer-readable code associatedwith a drug container storing a drug included in a first drug entry inthe formulary; automatically prompting a user to verify that an identityof the drug returned as a result of said reading the computer-readablecode with the code reader is consistent with information included on alabel associated with the drug container; receiving an input from theuser verifying the identity of the drug returned based on thecomputer-readable code is consistent with the information included onthe label; and after receiving the input from the user, storing anindication that the identity of the drug has been verified in the firstdrug entry associated with the drug in the formulary.
 12. The method ofclaim 11, wherein said receiving the plurality of drug entries comprisesreceiving, over a communication network, a formulary including theplurality of drug entries selected from a master drug database at aremotely-located computer terminal.
 13. The method of claim 12, whereinsaid reading, said automatically prompting, and said receiving the inputare performed after the formulary is created.
 14. The method of claim11, wherein said automatically prompting is performed only in responseto a first reading of the computer-readable code associated with thedrug with the code reader, and is not performed in response to asubsequent reading of the computer-readable code.
 15. The method ofclaim 11, further comprising transmitting a notification that the drughas been verified to a remote apparatus over a communication network tonotify an administrator authorized to access and edit a formularycomprising the plurality of drug entries that verification of the drughas been received.
 16. The method of claim 11, wherein the code readercomprises a barcode scanner, and the computer-readable code comprises abarcode, the method further comprising printing a label that iscompliant with a medical labeling standard.
 17. The method of claim 16,wherein said receiving the plurality of drug entries comprises receivinga formulary including the plurality of drug entries over a communicationnetwork, and replacing an existing formulary, in its entirety, with theformulary received over the communication network.